Product common object

ABSTRACT

Stored product management information in a first format for use by a first computerized system is transformed to readily make the stored product management information available for use in a second computerized system that utilizes a second format in a cost-efficient and time-efficient manner.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present patent application is a continuation of U.S. patent application Ser. No. 11/441,493, filed on May 26, 2006, now U.S. Pat. No. 8,200,539 entitled “Product Common Object” which is a continuation of U.S. patent application Ser. No. 10/751,008 filed Dec. 31, 2003, now U.S. Pat. No. 7,904,340 entitled “Product Common Object;” which claims the benefit of U.S. Provisional Application No. 60/457,474 filed Mar. 24, 2003, entitled “Product Common Object.” All are incorporated by reference herein in their entirety and for all purposes as if completely and fully set forth herein.

TECHNICAL FIELD

The present invention is directed to the field of data modeling in the context of enterprise resources planning, and more specifically to aspects of product life cycle management.

BACKGROUND

When new products are created or existing products are updated, the associated new and updated product definitions need to be communicated to various sub-processes that make up the product lifecycle management system, which in turn may be part of a multi-application integration system (MAIS).

For example, a front-office for sales and customer service can be treated as the source of all sales related product information. For purposes of explanation, assume that the front-office maintains and defines all sales catalogs, as well as defines bundled product definitions and configurable product definitions. The front-office can use customer feedback either to modify product definitions and requirements or to create new product definitions and requirements. When the new product definitions are created by the front-office, such new product definitions need to be made available in the back-office for engineering design and manufacturing systems. For example, the post sales, service and support activities information gathered by the front-office serve as feedback into the process for defining/analyzing customer requirements for a given product. Such information can be used by the back-office engineering/manufacturing systems to create a better product or improve existing products.

Similarly, the back-office engineering design and manufacturing systems may also initiate new product definitions or modify existing product definitions. For example, the engineers in the back-office may develop a new product. The new product information needs to be made available to the front-office (sales and service department of the company) so that the company can present the latest product offerings to customers.

The users of the front-office software computerized systems typically store data in forms usable by the front-office computerized system, which often differ significantly from the forms usable with back-office computerized systems.

Thus, when some or all aspects of product management are managed by both back-office and front-office computerized systems, there is a need to synchronize the product management information in both computerized systems. Generally, in order for front-office computerized systems to communicate with back-office computerized systems that are already being used, the user must manually regenerate data from the back-office computerized systems in forms usable by the front-office computerized systems, and vice versa. Such manual regeneration has several significant disadvantages, including: (1) it is often expensive; (2) it often requires a substantial amount of time to complete; (3) it must be repeated each time data changes in either the back-office system or the front-office system; and (4) it is prone to errors.

In view of the foregoing, an automated approach for transforming data used by a back-office computerized system for use by a front-office computerized system, and vice versa, is needed.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a high-level network diagram showing aspects of a computerized environment in which the facility operates, according to certain embodiments.

FIG. 1B is a block diagram showing some of the components typically incorporated in at least some of the computer systems and other devices on which the facility executes.

FIG. 2 is a high-level flow diagram that shows some steps performed by the facility.

FIG. 3 to FIG. 15 are data structure diagrams that illustrate the product common object model, according to certain embodiments.

DETAILED DESCRIPTION

According to certain embodiments, the synchronization of product management information addresses the needs of a company, which needs result in deploying multiple computer applications, obtained from multiple vendors of computer applications, in the company's product management system. The synchronization operation provides a user of the product management system the same view of the product management information across the various computer applications. All changes in the product management information need to be captured and made accessible to all relevant computer applications in the product management system. Thus, a common data storage model is needed for enabling users in the product management system to have the same view of the product management information across the various computer applications.

For purposes of explanation, assume that a company's product management system includes a front-office system for customer interfacing operations, such as sales, and customer service. Further, assume that the company's product management system also includes a back-office system that includes an engineering design and manufacturing applications, for example. The computer applications of the front-office system uses a data model that is distinct from the data model used in the back-office system's computer applications.

For example, assume that new or updated product management information is created in the front-office based on post sales, service and support activities information gathered by the front-office. Such information can be used by the back-office engineering/manufacturing systems to create a better product or improve an existing product. Thus, a common data storage model is needed so that the various computer applications used by the front-office can share the product management information with the back-office computer applications, and vice versa.

Product management information is not restricted to sales and engineering systems. Product lifecycle management can extend product management information out of engineering and manufacturing into other critical enterprise processes such as those related to planning, price costing, price listing, bill of materials, forecasting, etc.

Thus, when all systems within an enterprise have a consistent and accurate view of the product management information, improvement can be made with respect to the following metrics:

-   -   Time-to-Market: This is a key metric that tracks how long it         takes for a company to bring a new product to market. In times         of increasing competition and pricing pressure, time-to-market         is critical in ensuring that a company can maintain a         competitive advantage and profitability. Access to accurate         product information reduces the time to add new products to         sales catalogs, and reduces the time needed to prepare for         promotion and sales.     -   Configuration Accuracy: Configuration accuracy ensures that only         the latest and most accurate product information is available at         the point of sale or service. For example, if attributes of a         product have changed or if a product is obsolete, then such         changes would result in a configuration that is valid from the         front-office perspective but invalid from a back-office         perspective. Access to accurate product information results in a         reduction in the cost of updating product configuration         information in sales catalogs and in configuration engines.     -   Timely Orders: Accurate product management information enables         buyers to be notified of new product announcements in a timely         manner. Further, the timely creation of SKUs for new products         allows for the company to accept customer orders for such new         products.     -   Valid Orders: Inaccurate product management information would         result in incorrect orders being generated.

A software facility (hereafter “the facility”) for automatically converting product management information, is described. In some embodiments, the facility converts product management information from a form used by the source system to a form used by the target system. In certain embodiments, back-office systems are those that provide support for such functions as engineering, design, manufacturing, and financing. In certain embodiments, front-office system are those that provide support for such functions as sales and service to consumers. As previously explained, the flow of product management information may be bi-directional. In other words, product management information can be initiated from either the front-office product management system or from the back-office product management system.

When product management information is passed from the back-office product management system to the front-office product management system, then the back-office product management system is referred to as the source system and the front-office product management system is referred to as the target system. On the other hand, when product management information is passed from the front-office product management system to the back-office product management system, then the front-office product management system is referred to as the source system and the back-office product management system is referred to as the target system.

In some embodiments, such as embodiments adapted for converting product management information in the first source format, the facility converts product management information by converting the product management information that is in the first source format into an intermediate format. The intermediate format is then used to convert the product management information into the target format.

By performing such conversions, embodiments of the facility enable a user of a first computerized system who has stored product management information in a first format for use by the first computerized system to readily make the stored product management information available for use in a second computerized system that utilizes a second format in a cost-efficient and time-efficient manner.

FIG. 1A is a high-level network diagram showing aspects of a typical hardware environment in which the facility operates. FIG. 1A shows a source system 110, a target system 130, an integration server 120 and a network 150. Source system 110 stores product management information in a source format. There may be more than one source system. Target system 130 stores product management information in a target format. There may be more than one target system.

The facility (not shown) converts some or all product management information that is in the source format into the target format by using an intermediate format of the product management information. In certain embodiments, such conversions are performed with the aid of one or more other computer systems, such as integration server system 120. Components of the facility may reside on and/or execute on any combination of these computer systems, and intermediate results from the conversion may similarly reside on any combination of these computer systems.

The computer systems shown in FIG. 1A are connected via network 150, which may use a variety of different networking technologies, including wired, guided or line-of-sight optical, and radio frequency networking. In some embodiments, the network includes the public switched telephone network. Network connections established via the network may be fully-persistent, session-based, or intermittent, such as packet-based. While the facility typically operates in an environment such as is shown in FIG. 1A and described above, those skilled in the art will appreciate the facility may also operate in a wide variety of other environments.

FIG. 1B is a block diagram showing some of the components typically incorporated in at least some of the computer systems and other devices on which the facility executes, including some or all of the server and client computer systems shown in FIG. 1A. These computer systems and devices 100 may include one or more central processing units (“CPUs”) 101 for executing computer programs; a computer memory 102 for storing programs and data—including data structures—while they are being used; a persistent storage device 103, such as a hard drive, for persistently storing programs and data; a computer-readable media drive 104, such as a CD-ROM drive, for reading programs and data stored on a computer-readable medium; and a network connection 105 for connecting the computer system to other computer systems, such as via the Internet, to exchange programs and/or data—including data structures. While computer systems configured as described above are typically used to support the operation of the facility, those skilled in the art will appreciate that the facility may be implemented using devices of various types and configurations, and having various components.

It will be understood by those skilled in the art that the facility may transform product management information from a number of different source systems and from a number of different source software packages to a number of target systems and/or to a number of target software packages.

FIG. 2 is a high-level flow diagram that shows some steps typically performed by the facility in order to convert product management information from one or more source formats to the target format. At block 201, the facility extracts product management information from one or more source systems. At block 202, the facility converts the extracted information into an intermediate format. The intermediate format is described in greater detail herein, with reference to the common object data model. At block 203, the facility synchronizes the product management information from the source system with that of the target system by converting the product management information in intermediate format into the target format. After block 203, the steps as shown in FIG. 2 conclude.

The common object data model for product management may include some or all of the following information, according to certain embodiments:

-   -   Product Name     -   Product Part Number     -   Product Description     -   Product Identifier (different from product name)     -   Organization     -   Vendor Name     -   Vendor Part Number     -   Vendor Organization     -   Inventory Organization     -   Class     -   Attribute     -   Other service Information     -   Product Type     -   Unit of Measure     -   Effective Start Date     -   Effective End Date     -   Orderable     -   Saleable     -   Lead Time     -   Substitute Product     -   Related Product     -   Equivalent Product     -   Equivalent Product Primary Organization     -   Equivalent Product Vendor     -   Equivalent Product Vendor Organization     -   Class Name     -   Lead Time     -   Maximum Quantity     -   Minimum Quantity     -   Orderable Flag     -   Sales Product Flag     -   Serialized Product     -   Service Product     -   Ship Carrier     -   Shipping Via     -   Units in Inventory     -   Units in Inventory As Of a Certain Date

The common object data model for product management is herein referred to as a product common object model. FIG. 3 to FIG. 15 are data structures of the product common object model associated with product management. Such a product common object model illustrates sample intermediate data structures produced from corresponding product management information in the source format. The elements and associated sub-elements in the product data structure model as described herein are optional. In other words, the decision to include a given element or sub-element may vary from implementation to implementation. Further, the product common object model is designed to be flexible and thus, the definition of a given element or sub-element may vary form implementation to implementation depending of the needs of the enterprise.

The product common object model as described herein may be adapted and/or extended to represent various products for most industries. Further, the product common object data model may be used to satisfy requirements associated with customer orders, company assets, company business opportunities, product pricing, and product costing, for example.

In FIG. 3, the intermediate data structure used by the facility is represented by a listOfProduct element 300, which may include any number of product elements 310. One such illustrated product element is product element 400 as shown in FIG. 4.

In FIG. 4, product element 400 includes a product identifier (ID) element 402, a product baseData element 404 (contains basic information on the given product), a product salesData element 406 (contains sales information for the given product), a product configurationData element 408 (contains configuration data for the given product), a relatedProductLine element 410 (contains information on the product line that is associated with the given product), a product listOfPriceType element 412 (contains information on valid price types for the given product), a product listOfRelatedInvLoc element 414 (contains information on inventory locations that stock the given product), a listOfRelatedProduct element 416 (contains information on products that are related to the given product), a product listOfRelatedBusUnit element 418 (contains information on sales organizations that are authorized to sell the given product), and a product customData element 420 (contains customized data associated with the given product).

The product baseData element 404 is described in greater detail with reference to FIG. 5. The product salesData element 406 is described in greater detail with reference to FIG. 6. The product configurationData element 408 is described in greater detail with reference to FIG. 7. The relatedProductLine element 410 is described in greater detail with reference to FIG. 8. The product listOfPriceType element 412 is described in greater detail with reference to FIG. 9. The product listOfRelatedInvLoc element 414 is described in greater detail with reference to FIG. 10. The listOfRelatedProduct element 416 is described in greater detail with reference to FIG. 11. The product listOfRelatedBusUnit element 418 is described in greater detail with reference to FIG. 12.

In FIG. 5, the product baseData element 500 includes a product categoryCode element 502 (contains information on the product category code), a product description element 504 (contains product description information), a product effectiveEndDate element 506 (contains information on the product's validity end date), a product effectiveStartDate element 508 (contains information on the product's validity start date), a globalProductIdentifier element 510 (contains information on a global identifier for the given product, such as DUNS, ISBN, etc., which is often used in business-to-business relationships), a global ProductClassificationCode element 512 (contains information on the global classification code for the given product, wherein the global classification code may be set by an international standards body), a product globalSerialIdentifier element 514 (contains information on the global serial number for the given product, if the product is serialized), a product globalSpecialHandlingCode 516 (contains handling instructions for the given product), a product name element 518 (contains the name of the given product), a product number element 520 (contains the serial number of the given product, if the product is serialized), a product part Number element 522 (contains the part number of the given product), a product statusCode element 524 (contains status information associated with the given product, such as whether support is being phased out for the given product, for example), a product typeCode element 526 (contains type code information associated with the given product, such as savings account, checking account, etc., if the product is a banking service, for example), a product unitOfMeasureCode element 528 (such as kilogram or pound, for example), a product vendorPartNumber element 530 (contains the serial number used by the vendor associated with the given product).

FIG. 6 illustrates various elements that contain information related to sales of the given product, according to certain embodiments: In FIG. 6, the product salesData element 600 includes a product fieldReplaceableFlag element 602, which is a flag that indicates whether the product can be replaced by a field service engine. The product salesData element 600 includes a product leadTime element 604, which is the lead time that is needed for delivery of the product. Further, the product salesData element 600 includes a product maximumOrderQuantity element 606 (indicates a maximum quantity of the product per customer order), a product minimumOrderQuantity element 608 (indicates a minimum quantity of the product per customer order), a product revision element 610 (indicates a revision number, such as product configuration revision number or product design revision number), and a product orderableFlag element 612 that indicates whether the given product can be ordered or not. For example, a given product may be flagged as unorderable if the given product is being discontinued by the enterprise. The product salesData element 600 also includes a salesProductFlag element 614 (indicates whether the given product is merchandize as opposed to being a service), a product serviceFlag element 616 (indicates whether the given product is a service as opposed to being merchandize), a product serviceInstanceFlag element 618 (indicates whether the given product is a configurable service, such as a warranty service, for example), and a product serializedFlag element 620 (indicates whether the given product is to be serialized).

In FIG. 7, product configurationData element 700 includes a product configFlag element 702 (i.e., a configuration flag for the given product), and a product relatedClass element 704, which identifies the class from which configuration data is to be inherited by the given product, according to certain embodiments. The product relatedClass element 704 is described in greater detail herein with reference to FIG. 13.

FIG. 8 illustrates some elements that contain information with respect to the product line that is associated with the given product, according to certain embodiments. In FIG. 8, the relatedProductLine element 800 includes a productLine element 802, which contains identification information for identifying the product line associated with the given product. The productLine element 802 includes a product line indentification (ID) element 804, a product line baseData element 806, and a product line customData element 808 (contains any customized data that is associated with the product line). The product line baseData element 806 includes a product line description element 809 and a product line name element 810.

FIG. 9 illustrates some elements that contain information with respect to certain pricing aspects associated with the given product, according to certain embodiments. In FIG. 9, the product listOfPriceType element 900 includes any number of product priceType elements 902 (contains information on the valid price types for the given product). Each product priceType element 902 includes a product priceTypeCode element 904 (examples of price type codes are recurring charges, one-time charge, usage charge, etc.).

FIG. 10 illustrates some elements that contain information with respect to the inventory locations that stock the given product, according to certain embodiments. There may be multiple locations that stock the given product. In FIG. 10, the product listOfRelatedInvLoc element 1000 includes any number of product relatedInvLoc elements 1010 (contains the information on the inventory locations, such as warehouses or plants, that stock the given product). Each product relatedInvLoc element 1010 includes a product inventory location identification element 1012 (ID for identifying the inventory location for the given product), and an product inventoryData element 1014 (contains information on attributes of the given product in the context of the specific inventory location for the given product). The product inventoryData element 1014 is described in greater detail herein with reference to FIG. 14.

FIG. 11 illustrates some elements that contain information with respect to products that are related to the given product, according to certain embodiments. For example, a related product may be a parent product, an equivalent product, a substitute product, etc. In FIG. 11, the listOfRelatedProduct element 1100 includes any number of relatedProduct elements 1102 (such as parent product, an equivalent product, a substitute product, etc.). Each relatedProduct element 1102 includes a related product identification (ID) element 1104, a related product name element 1106, a related product number element 1108, and a related product typeCode element 1110 (example type codes are “parent”, “equivalent”, “substitute”, etc.).

FIG. 12 illustrates some elements that contain information with respect to sales or business organizations that are authorized to sell the given product, according to certain embodiments. In FIG. 12, the product listOfRelatedBusUnit element 1200 includes a product relatedBusUnit element 1202 (one of the sales organizations that is authorized to sell the given product). The product relatedBusUnit element 1202 includes a product sales or business organization identifier (ID) element 1204, and a productBusUnitData element 1206 (contains information on the sales or business-organization that is authorized to sell the given product). The productBusUnitData element 1206 is described in greater detail herein with reference to FIG. 15.

In FIG. 13, the relatedClass element 1300 includes a product related class identifier (ID) element 1302. The product related class element is part of the configuration data associated with the given product.

FIG. 14 illustrates some of the elements that describe attributes that are specific to the given product and that are specific to the inventory location for that given product, according to certain embodiments. In FIG. 14, product inventoryData element 1400 includes a product classificationData element 1402 (contains product inventory location classification data) and a product stockingData element 1404 (contains product inventory location stocking data). The product classificationData element 1402 includes a product movementClassCode element 1406 (i.e., classification code that indicates whether the given product is a slow moving product or a fast moving product as indicated by the number of counting cycles), and a product valueClassCode element 1408 (i.e., the given product is classified according to value, such as high value, medium value, low value, etc.).

Further, in FIG. 14, the product stockingData element 1404 includes a product allocateBelowSafetyStockLevelFlag element 1410 (such a flag indicates whether to allocate below the product safety stock level, in response to filling an order), a product autoSubstituteFlag element 1412 (such a flag indicates whether the given product is automatically substituted with another product when filling an order), a product autoAllocateFlag element 1414 (such a flag indicates whether the given product is automatically allocated), a product maxInventoryLevel element 1416 (indicates the maximum inventory level that can be maintained at the given inventory location with respect to the given product), a product minInventoryLevel element 1418 (indicates the minimum inventory level at which a re-stocking of the given product will be triggered at the given inventory location), and a product safetyStockLevel element 1420 (indicates the safe level at which the given product should be stocked at the given inventory location).

FIG. 15 illustrates some of the elements that contain information that is specific to a business or sales organization that is authorized to sell the given product, according to certain embodiments. In FIG. 15, productBusUnitData 1500 includes a product salesUnitOfMeasureCode element 1502, which is a sales unit of measure for the given product.

It will be appreciated by those skilled in the art that the above-described facility may be straightforwardly adapted or extended in various ways. For example, the facility may be used to transform various other kinds of inventory transaction information, and may be used to transform inventory transaction information between a variety of other formats.

In the foregoing specification, embodiments of the invention have been described with reference to numerous specific details that may vary from implementation to implementation. Thus, the sole and exclusive indicator of what the invention is, and what is intended by the applicants to be the invention, is the set of claims that issue from this application, in the specific form in which such claims issue, including any subsequent correction. Any express definitions set forth herein for terms contained in such claims shall govern the meaning of such terms as used in the claims. Hence, no limitation, element, property, feature, advantage or attribute that is not expressly recited in a claim should limit the scope of such claim in any way. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense. 

We claim:
 1. A method comprising: receiving a first product definition from a first source product application, wherein the first product definition is in a first source format; receiving a second product definition from a second source product application, wherein the second product definition is in a second source format; generating a first transformed product definition by transforming the first product definition using an intermediate product definition, wherein the transforming the first product definition is performed by an integration server, the transforming the first product definition uses a common object model, and the common object model defines a common format; generating a second transformed product definition by transforming the second product definition using the intermediate product definition, wherein the transforming the second product definition is performed by the integration server, and the transforming the second product definition uses the common object model; and generating a target product definition by transforming the first and the second transformed product definitions using a transformed product definition, wherein the transforming the first and the second transformed product definitions is performed by the integration server, and the target product definition is in a target format.
 2. The method of claim 1, wherein the first source format corresponds to the first source product application, and the second source format corresponds to the second source product application.
 3. The method of claim 1, wherein the transforming the first and the second transformed product definitions uses the common object model.
 4. The method of claim 1, the common object model comprises a list of product elements for defining a hierarchy of data elements, and the hierarchy of data elements comprises a plurality of product elements.
 5. The method of claim 4, wherein each of the plurality of product elements comprises one or more elements selected from a group comprising: a product identifier; a product base data element; a product sales data element; a product configuration data element; a related product line element for defining a product line element; a product list of price type element for defining a plurality of product price type elements; a product list of related inventory location element for defining a plurality of product related inventory location elements for the product; a list of related product element for defining a plurality of related product elements; a product list of related business unit element for defining a product related business unit element; and a product custom data element.
 6. The method of claim 1, further comprising: obtaining modified product definitions associated with at least one to-be-modified product from the first source product application, wherein the modified product definitions are in the first source format; transforming the modified product definitions into intermediate modified product definitions, wherein the intermediate modified product definitions are in the common format; and transforming the intermediate product definitions into transformed modified product definitions, wherein the transformed modified product definitions are in the target format.
 7. The method of claim 6, further comprising: communicating the transformed modified product definitions to the one or more target product applications; using the transformed modified product definitions to create one or more data records in the target format and to update one or more existing data records in the target format to reflect the modified product; and causing to modify the at least one to-be-modified product based on the one or more data records and the updated existing data records if the one or more target product applications is tasked to modify the at least one to-be-modified product.
 8. The method of claim 1, wherein the transforming the first product definition uses the common format, the transforming the second product definition uses the common format, and the transforming the first and the second transformed product definitions uses the common format.
 9. The method of claim 8, wherein the common format comprises a common set of fields, wherein one or more common fields of the common set of fields corresponds to one or more respective source fields in a first source set of fields, the first product definition comprises the first source set of fields, the one or more common fields further corresponds to one or more respective target fields in a target set of fields, and the target product definition comprises the target set of fields.
 10. The method of claim 9, wherein at least one source field of the source set of fields is not among the common set of fields, and at least one target field of the target set of fields is not among the common set of fields.
 11. The method of claim 9, wherein the one or more common fields of the common set of fields further corresponds to one or more respective source fields in a second source set of fields, and the second product definition comprises the second source set of fields.
 12. A system, comprising: one or more processors; and a facility, wherein the facility is configured to receive a first product definition from a first source product application, wherein the first product definition is in a first source format, receive a second product definition from a second source product application, wherein the second product definition is in a second source format, generate a first transformed product definition by transforming the first product definition using an intermediate product definition, wherein the facility performs the transforming the first product definition using a common object model, and the common object model defines a common format, generate a second transformed product definition by transforming the second product definition using the intermediate product definition, wherein the facility performs the transforming the second product definition using the common object model, and generate a target product definition by transforming the first and the second transformed product definitions using a transformed product definition, wherein the target product definition is in a target format, and the facility is configured to be executed using the one or more processors.
 13. The system of claim 12, wherein the facility transforms the first and the second transformed product definitions using the common object model.
 14. The system of claim 12, wherein the facility transforms the first product definition using a common format, the facility transforms the second product definition using the common format, and the facility transforms the first and the second transformed product definitions using the common format.
 15. The system of claim 12, wherein the common format comprises a common set of fields, wherein one or more common fields of the common set of fields corresponds to one or more respective source fields in a first source set of fields, the first product definition comprises the first source set of fields, the one or more common fields further corresponds to one or more respective target fields in a target set of fields, and the target product definition comprises the target set of fields.
 16. The system of claim 15, wherein at least one source field of the source set of fields is not among the common set of fields, and at least one target field of the target set of fields is not among the common set of fields.
 17. A computer program product comprising: a plurality of instructions, comprising a first set of instructions, executable on a computer system, configured to receive a first product definition from a first source product application, wherein the first product definition is in a first source format, a second set of instructions, executable on the computer system, configured to receive a second product definition from a second source product application, wherein the second product definition is in a second source format, a third set of instructions, executable on the computer system, configured to generate a first transformed product definition by transforming the first product definition using an intermediate product definition, wherein the transforming the first product definition uses a common object model, and the common object model defines a common format, a fourth set of instructions, executable on the computer system, configured to generate a second transformed product definition by transforming the second product definition using the intermediate product definition, wherein the transforming the second product definition uses the common object model, and a fifth set of instructions, executable on the computer system, configured to generate a target product definition by transforming the first and the second transformed product definitions using a transformed product definition, wherein the target product definition is in a target format; and a tangible computer-readable storage medium, wherein the instructions are encoded in the tangible computer-readable storage medium.
 18. The computer program product of claim 17, wherein the transforming the first and the second transformed product definitions uses the common object model.
 19. The computer program product of claim 17, wherein the transforming the first product definition uses a common format, the transforming the second product definition uses the common format, and the transforming the first and the second transformed product definitions uses the common format.
 20. The computer program product of claim 17, wherein the common format comprises a common set of fields, wherein one or more common fields of the common set of fields corresponds to one or more respective source fields in a first source set of fields, the first product definition comprises the first source set of fields, the one or more common fields further corresponds to one or more respective target fields in a target set of fields, and the target product definition comprises the target set of fields.
 21. The computer program product of claim 20, wherein at least one source field of the source set of fields is not among the common set of fields, and at least one target field of the target set of fields is not among the common set of fields.
 22. The method of claim 1, wherein the intermediate product definition is in the common format.
 23. The system of claim 12, wherein the intermediate product definition is in the common format.
 24. The computer program product of claim 17, wherein the intermediate product definition is in the common format. 